Study Plan
2110 Topo
| Component | Computes Offset & Delay? | What It Actually Does |
|---|---|---|
| Slave / Endpoint (cameras, servers, multiviewers, etc.) | Yes — main calculator | Collects the 4 timestamps (T1–T4), runs the offset and delay formulas, continuously adjusts its local clock via servo loop. |
| Grandmaster / Master Clock | No | Only provides accurate timestamps (T1 for Sync, T4 for Delay_Response). Keeps it simple and scalable. |
| Transparent Clock (in switches) | No (but compensates) | Measures residence time inside the switch and adds correction fields to Sync/Follow_Up messages — helps slave's math stay accurate. |
| Boundary Clock (edge clocks in switches) | Yes (as slave to upstream) | Acts as slave → computes offset/delay for itself → then becomes master to downstream devices, regenerating clean time signals. |
| Unaware switch/router | No | Adds uncontrolled delay/jitter — avoid for precision; can degrade accuracy over hops. |
Key takeaway: The endpoint (slave) does the heavy lifting on calculations. Boundary clocks (common in broadcast switches) also compute when they act as slaves upstream, making them crucial for scaling and isolating network segments in large or multi-facility setups.
For more details, check the linked pages in your PTP section or dive into SMPTE ST 2059-2 profile specifics.